[NV] minimax-m3-b200/b300: update fp8 STP to vLLM nightly - #2336

This PR bumps the image: field for both the B300 and B200 MiniMax-M3 FP8 STP configs in configs/nvidia-master.yaml from vllm/vllm-openai:minimax-m3-0618-x86_64-cu130 to vllm/vllm-openai:nightly-4080263bb2c5d10deac17aaeb88e0823bc35bca9, but it leaves the explanatory block comments directly above each entry untouched. Both comments read (identically, word for word): "M3 support has not shipped in a stable vLLM release; the dedicated vllm/vllm-openai:minimax-m3-0618-x86_64-cu130 image is built from the m3_release branch (vllm-project/vllm#45381)." That sentence now names a container tag the config no longer references and asserts a provenance story ("dedicated ... image ... built from the m3_release branch") that no longer applies to a generic nightly build.

The two locations are:

• Lines ~7322-7329 (comment) / line 7331 (image:) above minimaxm3-fp8-b300-vllm
• Lines ~7402-7410 (comment) / line 7412 (image:) above minimaxm3-fp8-b200-vllm

Nothing in the PR or the surrounding YAML would catch this: comments are not validated against the fields they describe, there is no schema or lint rule tying image: values to comment text, and the diff hunk for the image-line change does not include the comment block above it, so a reviewer skimming the diff would only see the new image: value, not the stale sentence sitting just outside the hunk context.

The impact is documentation-only — nothing breaks at runtime, CI, or in the benchmark sweep, since the comment is never parsed or executed. The risk is purely that a future engineer reading this config (e.g., to decide whether to bump the image again, or to understand why a "dedicated" image was pinned) will be misled into thinking the current nightly image is still the special m3_release-branch build tied to vllm-project/vllm#45381, when it is actually an unrelated nightly snapshot.

Step-by-step proof:

1. Before this PR: image: vllm/vllm-openai:minimax-m3-0618-x86_64-cu130 on both entries, matching the comment's claim of "the dedicated ... image ... built from the m3_release branch."
2. This PR's diff changes only the image: line to vllm/vllm-openai:nightly-4080263bb2c5d10deac17aaeb88e0823bc35bca9 for both minimaxm3-fp8-b300-vllm and minimaxm3-fp8-b200-vllm.
3. The comment block immediately above each entry is untouched by the diff and still names the old minimax-m3-0618-x86_64-cu130 tag and the m3_release-branch rationale.
4. Reading the file post-merge, a reader sees image: vllm/vllm-openai:nightly-... directly under a comment that describes a completely different image and its provenance — a direct contradiction between comment and code.

Fix: update (or trim) the comment in both places to reflect that a nightly vLLM build is now used, e.g., replace the "dedicated ... m3_release branch" sentence with something like "a nightly vLLM build is used until M3 support lands in a stable release," or simply drop the specific tag/PR reference since it no longer applies.

What the rule requires: AGENTS.md line 7 states explicitly:

PR and GitHub-issue titles & descriptions must be bilingual — include a Simplified Chinese version in addition to English. Title format: <English title> / <中文标题>. In the PR/issue body, follow the English content with its Chinese translation (e.g. a ## 中文说明 section mirroring the summary...). This applies to every PR and every issue.

The only carve-outs are the CODEOWNER sign-off template (which must stay English-verbatim so the verifier bot can match its exact trigger phrase) and bot-generated comments. Neither exception covers the PR author's own title or Summary section.

How this PR violates it: The PR title is [NV] minimax-m3-b200/b300: update fp8 STP to vLLM nightly — English only, with no / <中文标题> suffix. The description consists solely of an English ## Summary section (image bump, --stream-interval 32, dropping the MSA contiguity patch); there is no ## 中文说明 section mirroring it.

Why this isn't caught automatically: Nothing in this PR's diff (the benchmark scripts, configs/nvidia-master.yaml, or perf-changelog.yaml) enforces or validates the bilingual title/description requirement — it's a human/PR-metadata convention rather than something checked by the changelog validator or the sign-off bot. The sign-off bot only checks for the literal English phrase As a PR reviewer and CODEOWNER, I have reviewed this and have in a reviewer comment; it has no logic inspecting the PR title or Summary body for Chinese content. So a purely English title/description sails through CI untouched, and the requirement can only be caught by review (human or otherwise) against AGENTS.md.

Step-by-step proof:

1. Open AGENTS.md and read line 7 — the bilingual title/description mandate applies to "every PR and every issue," with the title format <English title> / <中文标题>.
2. Look at the PR metadata: title = [NV] minimax-m3-b200/b300: update fp8 STP to vLLM nightly. Split on / — the only / present is part of minimax-m3-b200/b300, a hardware pairing, not a <中文标题> suffix. There is no Chinese text anywhere in the title.
3. Look at the PR body: it contains only ## Summary with English bullet points. Search for 中文 or any CJK characters in the body — none are present, so there's no ## 中文说明 section as required.
4. Confirm no exception applies: this is not the CODEOWNER sign-off template (those are the two github-actions[bot] timeline comments, not the PR title/description) and not a bot-generated comment — it's the author's own title and Summary.
5. Conclusion: the PR violates the explicit, repo-mandated bilingual requirement.

Impact and fix: This is a process/documentation-convention gap, not a functional defect — nothing in the benchmark scripts, config, or changelog entry is incorrect, and no CI job or benchmark run will fail because of it. The fix is straightforward: rename the title to [NV] minimax-m3-b200/b300: update fp8 STP to vLLM nightly / <中文标题> and append a ## 中文说明 section to the body mirroring the English Summary (bump image, set --stream-interval 32, drop the MSA patch since it's fixed upstream), following the translation quality bar described elsewhere in AGENTS.md (natural technical Chinese, keeping model names/flags/SKUs in English).